[Python] TypeSpec migration for azure-mgmt-security#46465
[Python] TypeSpec migration for azure-mgmt-security#46465ChenxiJiang333 wants to merge 15 commits intoAzure:mainfrom
Conversation
ChenxiJiang333
force-pushed
the
sdk-azure-mgmt-security
branch
2 times, most recently
from
84b838a to
ae2f381
Compare
ChenxiJiang333
force-pushed
the
sdk-azure-mgmt-security
branch
4 times, most recently
from
5872835 to
4539356
Compare
ChenxiJiang333
force-pushed
the
sdk-azure-mgmt-security
branch
from
4539356 to
d0eb7b5
Compare
|
Hi @msyyc @ChenxiJiang333 — this PR was just marked as ready for review. Could you provide an ETA for when this can be reviewed and merged? The Microsoft.Security service team is waiting on this SDK release. We understand there are CI failures related to a Python emitter bug (duplicate schema names from LRO + @@OverRide). Is there a timeline for the upstream fix, or is there a workaround we can help with? cc @welovej |
Sorry, this pr is only for debug. Please let security service team follow https://eng.ms/docs/products/azure-developer-experience/plan/release-plan-create to create a release plan for sdk release. |
[Python] TypeSpec migration for azure-mgmt-security
Spec PR: Azure/azure-rest-api-specs#41888
Pre-migration swagger source: specification/security/resource-manager@5edf687e
Default tag
package-composite-v3contains multiple API versions:2015-06-01-preview/2017-08-01/2017-08-01-preview/2019-01-01/2019-01-01-preview/2019-08-01/2020-01-01/2021-05-01-preview/2021-10-01-preview/2022-01-01/2022-01-01-preview/2022-05-01/2022-07-01-preview/2023-01-01-preview/2023-02-15-preview/2023-05-01/2023-05-01-preview/2023-11-15/2023-12-01-preview/2024-08-01/2024-08-01-preview/2025-05-04/2025-09-01-preview/2025-10-01-preview/2025-11-01-preview/2026-01-01/2026-04-01-previewBreaking Change Analysis Summary
@@clientNamedecorators in spec PR)Spec Mitigation PR
welovej/azure-rest-api-specs#15
Mitigated Breaking Changes (6 items)
SecurityCenter→SecurityManagementClient@@clientNameto restoreSecurityCenterAadConnectivityStateEnum→AadConnectivityState@@clientNameto restoreAadConnectivityStateEnumExternalSecuritySolutionKindEnum→ExternalSecuritySolutionKind@@clientNameto restoreExternalSecuritySolutionKindEnumProtocolEnum→Protocol@@clientNameto restoreProtocolEnumKindEnum→Kind@@clientNameto restoreKindEnumStatuscollides with modelStatus@@clientNameto rename toStatusEnumAccepted Breaking Changes (by category)
*List)AlertList,PricingList,SecurityConnectorsListCloudErrorAutoGenerated*,ErrorDetailAutoGenerated*OnPremiseResourceDetails,Software,Code,LocationPricing.pricing_tier,IoTSecuritySolutionModel.workspaceMdeOnboardingsOperations.list,SecurityOperatorsOperations.listOperationResult.capitalize(code report artifact)OperationResultenum→modelOperationResultStatusenum__init__methods removedAadConnectivityState.__init__,Kind.__init__ActiveConnectionsNotInAllowedRange,AmqpC2DMessagesNotInAllowedRangePython Codegen Bug
@typespec/http-client-python@0.28.3) has a bug causingValueError: We have already generated a schema with name createOrUpdateRequest. Root cause: LRO operations with@@overridegenerate duplicate body model instances with the same name. A local pygen patch was applied to work around this. This should be tracked at https://github.com/microsoft/typespec/issues.Additional collisions found:
ArcAutoProvisioningGcp(2x),VmScannersGcp(2x) from discriminated subtypes, andStatusmodel/enum name collision.